home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
033a
/
upchk23f.zip
/
UPCHECK.DOC
< prev
next >
Wrap
Text File
|
1992-01-21
|
14KB
|
391 lines
UPCHECK DOCUMENTATION
Version 2.3f
Written By
Chris Phillips
--------------------
DISCLAIMER
----------
This software is provided "As Is". All responsibility and risk, in
installing and running this program and its associated files, is taken on
completely by the person using this software. This software comes without
any warranty, expressed or implied. If you do not agree with the above,
please don't use this software.
INTRODUCTION
------------
UPCHECK is a utility written for SPITFIRE Bulletin Board Systems to provide
Sysops a quick and easy method of testing uploaded files. UPCHECK will not
only test uploaded files for viruses and compression integrity, but also
add the BBS's unique ZIP comment, if desired. In addition to ZIP, UPCHECK
v2.3f also provides support for ARC, LZH, PAK and ARJ file compression
techniques. It should be noted, that if you want UPCHECK to add your ZIP
comment you must have the ZIPCOMNT.EXE program from ZIP-KIT9.ZIP, if you want
UPCHECK to test .GIF files you must have the TESTGIF.EXE program from
GIFT40B.ZIP, and if you want UPCHECK to test .TD0 files (Teledisked files)
you must have the TDCHECK.EXE program from TDCHK110.ZIP. All these files
are available from most BBS's.
Much thanks must go out to Mike Woltz for writting SPITFIRE, the best in
Bulletin Board Software!
CONFIGURING UPCHECK
--------------------
UPCHECK can be used to check uploaded files immediately after they
are uploaded and while the caller is still online or after the
caller has logged off and SPITFIRE is in between callers. One of
the first things you must decide is in what mode you intend to run
UPCHECK. If UPCHECK is to be run online, the SFEXTUP<x>.BAT will
require modification and if UPCHECK is to be run in between callers,
a SFINIT.BAT must be set up. Sample batch files are included in
the UPCHECK23.ZIP distribution package.
*NOTE*
UPCHECK can only be run online when a caller uses an external protocol!
Regardless of how you decide to run UPCHECK, unzip the distribution
package into the directory from which you intend to run UPCHECK.
You will notice a file included in UPCHECK23.ZIP called UPCHKCFG.EXE.
From the DOS prompt, type:
UPCHKCFG
to configure UPCHECK to run on your system.
Page 2
Configuration for Upcheck Ver 2.3f
(P)rograms Setup
(A)dditional Set parameters
(U)pload Area
(F)file Conversion
(S)how Current Configuration
(Q)uit w/Save
(X) Quit wo/Save
When the (P)rograms Setup option is selected, prompts will appear asking
whether the feature displayed should be enabled, ie:
Enable ZIP Y/(N) ?
*Note
This will allow you to enable processing of .ZIP files.
If you pick "Y" you will then be prompted with:
Path to PKUNZIP including extension
Was C:\UTIL\PKUNZIP.EXE Hit Enter to accept
You will then be prompted for the following files:
TDCHECK - TDCHECK.EXE Teledisked File Checker
GIFTEST - TESTGIF.EXE .GIF File Checker *
ZIPCOMNT - ZIPCOMNT.EXE ZIP Commenter *
ARC - PKXARC.COM .ARC Program
LZH - LHA.EXE .LHA Program
ARJ - ARJ.EXE .ARJ Program
PAK - PAK.EXE .PAK Program
SCAN - SCAN.EXE .Virus Scanner *
Any of these programs maybe turned on or off.
Files followed by a * will also prompt you with the following:
Command Line Parameters to use
Was * Hit Enter to accept
*Note
Another new feature of Upcheck ver 2.3f is to allow the user to specify
different command line parameters to 3 of the programs that are called by
UPCHECK. If for example you use a program other that ZIPCOMNT.EXE you may
wish to specify something other than a * as it's parameter. As you may
have already noticed , * is the default parameter for use with ZIPCOMNT.EXE.
In the same manner you may also use different parameters with your virus
scanner and your gif tester.
IMPORTANT: Whatever you specify for your alternate comment program the
parameters must indicate to that program to do ALL ZIPs in the current
directory.
When the (A)dditional Setup parameters option is selected you will be
prompted for the following:
Use Ramdisk for Work area ? Y/(N) *See note below about using this option!
*Note
UPCHECK now allows the user to use a Ramdisk as a "work" area. This is
especially useful when You have plenty of memory and would like to cut
down unnecessary wear and tear on your hard disk. When Extracting archives
upcheck would extract them to the ramdisk for scanning by your preferred
virus scanner. YOU MUST ENSURE THAT YOU HAVE A LARGE ENOUGH RAMDISK ! If
there is insufficient disk space available then NO ERROR will occur. I
would recommend at least 1-2 megs. Only 1 archive at a time will occupy
space in the ramdisk. ie. If four ZIPs are uploaded, they will be extracted
only one at a time into the ramdisk. any subsequent archives within the
file will still be extracted so this could eat up the space rather quickly.
If there are any problems encountered with this feature please let me know.
As far as I can tell , Upcheck will still function normally but be unable to
scan the entire contents of an extremely large archive.
If you pick "Y" you will then be prompted with:
Ramdisk Drive Designation
Was D: Hit Enter to accept
You will then be prompted with the following:
Enter Path for BAD FILES to be moved to
Was C:\BAD Hit Enter to accept
*Note
This is where you want files that have failed for one reason or
another to be moved to, this path MUST exist!
Path and Name of The List of executable files not to check
Was C:\UTIL\NOCHECK.DAT Hit Enter to accept
*Note
NOCHECK.DAT is a file that you may create to list files that reside
in the directory from where UPCHECK is executed that you wish to exclude
from integrity checking. For instance, if you are running UPCHECK online
from your external protocol path, you might want to include such files as
DSZ.EXE, LYNX.EXE, JMODEM.EXE etc. in your NOCHECK.DAT file. A sample
NOCHECK.DAT is included in the distribution package.
Path and Name of Log File
Was C:\SF\WORK\HEYSYSOP.LOG Hit Enter to accept
*Note
This is the .LOG file which UPCHECK will write to telling you what files
were checked and if any files failed.
ONLINE mode Y/(N)?
*Note
This is telling UPCHECK to write to the port so that the caller knows what
is going on, otherwise the caller may think your boards has "hung" when
testing a large file or running on a slow system.
If you pick "Y" you will then be prompted with:
ComPort to use { 1-4 }
When the (U)load Area option is selected you will be prompted for
the following:
Path to UPLOAD file area {hit enter to disable moving files}
*Note
Use this feature if you are running UPCHECK from the SFINIT.BAT file so
that the files being tested are moved from your "private" upload area to
a public area. File moving should be disabled if you are running online!
The description will also be moved from the original SFFILES.BBS to the
SFFILES.BBS in the area you you specify here. If no UPLOAD file area is
entered, when UPCHECK is completed its testing, the files will not be
moved but remain in the current directory.
When the (F)ile Conversion option is selected you will be prompted
for the following:
Convert All Archive Formats to a specific Format ? Y/(N)
*Note
This will allow you to convert any .ARJ, .PAK, etc...to a single
compression format that you board uses.
If you do a (S)how Current Configuration you will see the following:
Path to PKUNZIP : C:\UTIL\PKUNZIP.EXE
Path to ZIPCOMNT : C:\UTIL\ZIPCOMNT.EXE executed with *
Path to PKXARC : C:\UTIL\PKXARC.EXE
Path to PAK : C:\UTIL\PAK.EXE
Path to LHARC : C:\UTIL\LHA.EXE
Path to ARJ : C:\UTIL\ARJ.EXE
Path to SCAN : C:\UTIL\SCAN.EXE executed with /nomem /a
Path to TDCHECK : Disabled
Path to GIFTEST : C:\UTIL\TESTGIF.EXE executed with
Path to Log file : C:\SF\WORK\HEYSYSOP.LOG
Path to NOCHECK file : C:\UTIL\NOCHECK.DAT
Ramdrive For Work Area :Disabled
Location for Bad Files : C:\BADFILES
Convert Files : Disabled
ONLINE use : FALSE
Path to UPLOAD area :Moving Files Has Been Disabled
*Note
This will of course change to suit what you setup.
You must make sure that your paths to all files and directories listed in
the UPCHKCFG program are correct!
Page 3
RUNNING UPCHECK ONLINE
----------------------
When using UPCHECK online, it can only be configured to check files
that are uploaded using external protocols. You will need to modify
your SFEXTUP<X>.BAT to include the additional line:
UPCHECK
after the upload is completed and before the files are moved or
copied to the uploaded files directory. A sample, SFEXTUPA.BAT using
ZModem file transfer protocol might look like this:
@ECHO OFF
CD\SF\EXT
DSZ %2 handshake on pB8192 pd0 rz -m -r -rr
UPCHECK L
MUV %3 %4
REM The above "MUV" command must not be used in SPITFIRE v3.2 or higher!
CD\SF
ECHO ON
Page 4
A similar example using batch uploads might appear as below:
@ECHO OFF
CD\SF\EXT
DSZ %2 handshake slow pB8192 pd0 rz -m -r -rr
UPCHECK L
IF EXIST %3 MUV %3 %4
IF EXIST %5 MUV %5 %4
IF EXIST %6 MUV %6 %4
IF EXIST %7 MUV %7 %4
IF EXIST %8 MUV %8 %4
IF EXIST %9 MUV %9 %4
REM The above "MUV" commands must not be used in SPITFIRE v3.2 or higher
CD\SF
ECHO ON
MUV is Buffalo Creek's file moving utility. If MUV is not available
the files could be copied to the upload directory and then erased
from the external protocol directory just as easily.
Remember when using UPCHECK in the online mode to specify UPCHECK's
configuration for ONLINE use as TRUE and designate the appropriate Comm
Port.
RUNNING UPCHECK OFFLINE
-----------------------
To run UPCHECK between callers on the BBS, create or modify your
SFINIT.BAT to include the following:
@ECHO OFF
REM CHANGE TO YOUR PRIVATE UPLOAD DRIVE AND DIRECTORY
CD\PRIVUP
REM RUN UPCHECK IN THIS AREA
UPCHECK
REM CHANGE BACK TO YOUR SPITFIRE HOME DRIVE AND DIRECTORY
CD\SF
ECHO ON
Remember when using UPCHECK in the offline mode to specify UPCHECK's
configuration for ONLINE use as FALSE and designate the appropriate
upload files directory.
Page 5
COMMAND LINE PARAMETERS
-----------------------
At anytime, you need help regarding usage of UPCHECK's command line
parameters, type the following at the DOS prompt:
UPCHECK ?
This will provide information on the various command line parameter
options that are available with UPCHECK.
In addition to ? (help), UPCHECK uses the following command line parameters:
UPCHECK U=Directory
would move file(s) that pass UPCHECK's testing to the directory specified
here. The directory must be a valid DOS directory. Using UPCHECK U=
without any directory specified checks files in the current directory
without moving them when testing is completed.
UPCHECK L
would turn on logging of each file that is tested
UPCHECK P=#
where # indicates the comm port that is to be used. Note that the ONline
use is also set by this command.
Although, all command line parameters can be used together in any order,
the use of the P=<#> command will not allow files to be moved. So
UPCHECK L U=C:\SF\NEWUPS P=2
would set the ONline mode, therefore, no files would be moved.
Also note, using command line parameters with UPCHECK overrides the
appropriate settings established with UPCHKCFG.
By using the command parameter U=, it is possible to run UPCHECK from the
DOS command line so that it checks the files but does not move them. To
do this, simply run UPCHECK from the directory you wish to have checked
using the following command:
UPCHECK L U=
If you have any special requirements please
leave mail for me on The HOBBIT HOLE BBS as listed below.
REGISTRATION
------------
CHECKUP is NOT crippled in any way. Nor is it timed to cease operating
after a pre defined period of time. The shareware version operates
exactly as the registered version. The only difference between the
shareware version and the registered version is that the registered
version will display: Registered to <Sysop's name> of <BBS name> and
the shareware version denotes it is an unregistered version.
If you find this software beneficial please send the $10 registration fee
to:
Chris Phillips
61 Old Milton Rd
Rochester N.H. 03868
If you experience any problems or have any suggestions or requirements
please contact either myself or the SysOp of:
The Hobbit Hole BBS
(207)490-2159
300-38,400 Bauds
Using a US Robotics Dual Standard Modem